Add debugger tip to section "Trace a Tree Creation Site" of the contributing guide #18098
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I though "auto-merge (squash)" would still create a merge commit, but I'm not so sure anymore, is it okay to use it, or should I squash first and then do a normal (auto-)merge ? |
dwijnand
approved these changes
Jun 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While obvious in hindsight, there's already a lot of information to digest about the compiler, so these kinds of tips would hopefully help quite a bit
There is an argument to be made this adds even more information, but hopefully by starting with "If you are using a debugger", people who it does not concern can ignore it without burdening their mind